Peer-level control of industrial automation system components

ABSTRACT

Embodiments of this present disclosure may include a system that includes a first network device. The first network device may perform an operation according to a device configuration file. The system may also include a second network device that directly communicatively couples to the first network device through a peer-to-peer (P-P) communication network. The second network device may include a backup file of the device configuration file. The second network device may transmit the backup file of the device configuration file to the first network device in response to detecting that the first network device is lacking the device configuration file.

BACKGROUND

This disclosure relates generally to systems and methods for providing acontrol and monitoring system within an industrial automation system.More particularly, embodiments of the present disclosure are directedtoward systems to provide a self-healing, peer-to-peer communicationnetwork within the industrial automation system.

This section is intended to introduce the reader to various aspects ofart that may be related to various aspects of the present techniques,which are described and/or claimed below. This discussion is believed tobe helpful in providing the reader with background information tofacilitate a better understanding of the various aspects of the presentdisclosure. Accordingly, it should be understood that these statementsare to be read in this light, and not as admissions of prior art.

Industrial automation systems may include automation control andmonitoring systems. The automation control and monitoring systems maymonitor statuses and/or receive information from a wide range ofdevices, such as valves, electric motors, a wide range of sensors, othersuitable monitoring devices, or the like. One or more components of theautomation control and monitoring systems, such as programmingterminals, automation controllers, input/output (I/O) modules,communication networks, human-machine interface (HMI) terminals, and thelike, may use the statuses and/or received information to provide alertsto operators to change or adjust operation of one or more components ofthe industrial automation system (e.g., such as adjusting operation ofone or more actuators), to manage the industrial automation system, orthe like.

The components described above may operate in coordination with acontrol system. An example of a control system may be a programmablelogic controller (PLC) or a programmable logic device (PLD). The controlsystem may receive the statuses and/or information from the wide rangeof devices, and use the statuses and/or information to make controldecisions. An example of a control decision is determining whether toslow or halt operation of a motor or load. The components describedabove and/or the control system may operate according to stored deviceconfigurations. A device configuration may include processinginstructions, settings, operating ranges, indications of connections toother components within the industrial automation system, or the like,and may be used to customize an operation of the components and/or thecontrol system to a particular process. When components and/or thecontrol system are replaced, the device configuration may be lost andmay be reinstalled for the replacement component and/or control system.The replacement process may be a lengthy process that introducesopportunities for operator error. Furthermore, in some cases, aconfiguration manager software may be used to replace the configurationof the component and/or control system, thereby increasing time andprocessing resources used to prepare the replacement component and/orcontrol system for use.

SUMMARY

A summary of certain embodiments disclosed herein is set forth below. Itshould be understood that these aspects are presented merely to providethe reader with a brief summary of these certain embodiments and thatthese aspects are not intended to limit the scope of this presentdisclosure. Indeed, this present disclosure may encompass a variety ofaspects that may not be set forth below.

In one embodiment, a system may include a first network device thatperforms an operation according to a device configuration file. Thesystem may also include a second network device that directlycommunicatively couples to the first network device through apeer-to-peer (P-P) communication network. The second network device mayinclude a backup file of the device configuration file. The secondnetwork device may transmit the backup file of the device configurationfile to the first network device in response to detecting that the firstnetwork device is lacking the device configuration file.

In another embodiment, a method may include detecting, via a firstnetwork device, that a second network device is lacking a deviceconfiguration file. The first network device and the second networkdevice may couple to each other through a peer-to-peer network for anindustrial automation system. The method may also include transmitting,via the first network device, a backup configuration file thatcorresponds to the device configuration file to the second networkdevice in response to detecting that the second network device islacking the device configuration file. The second network device mayperform an operation within the industrial automation system in responseto a setting defined by the backup configuration file.

In yet another embodiment, a tangible, non-transitory computer-readablemedium may store instructions executable by a processor of an electronicdevice that, when executed by the processor, cause the processor todiscover multiple data endpoints. Each data endpoint of the plurality ofdata endpoints may correspond to a respective network device coupled toa P-P communication network. The instructions may also cause theprocessor to generate a device configuration file for a first networkdevice of the P-P communication network based on respective dataendpoints of the data endpoints associated with the first networkdevice. The instructions may also cause the processor to transmit thedevice configuration file to the first network device. The first networkdevice may perform an operation based on the device configuration file.The instructions may also cause the processor to transmit the deviceconfiguration file to a second network device of the P-P communicationnetwork. The second network device may transmit the device configurationfile to the first network device as a backup configuration file inresponse to detecting that the first network device is lacking thedevice configuration file.

DRAWINGS

These and other features, aspects, and advantages of the presentdisclosure will become better understood when the following detaileddescription is read with reference to the accompanying drawings in whichlike characters represent like parts throughout the drawings, wherein:

FIG. 1 is a perspective view of an example industrial automation system,in accordance with an embodiment;

FIG. 2 is a block diagram of an example industrial control system of theindustrial automation system of FIG. 1, in accordance with anembodiment;

FIG. 3 is a block diagram of an example local control system of theindustrial control system of FIG. 2, in accordance with an embodiment;

FIG. 4 is a block diagram of a peer-to-peer communication network of theindustrial automation system of FIG. 1 after a device replacement, inaccordance with an embodiment;

FIG. 5 is a flowchart of a method for generating a backup configurationfile of a device configuration file via the peer-to-peer communicationnetwork of FIG. 4, in accordance with an embodiment;

FIG. 6 is a flowchart of a method for performing a replacement of adevice configuration file associated with the peer-to-peer communicationnetwork of FIG. 4, in accordance with an embodiment;

FIG. 7 is a flowchart of a method for generating a device configurationfile and a backup device configuration file using a local controlsystem, in accordance with an embodiment;

FIG. 8 is a block diagram of the peer-to-peer communication network ofFIG. 4 in a smart wire configuration, in accordance with an embodiment;

FIG. 9 is a block diagram of logical couplings of the peer-to-peercommunication network of FIG. 4 in the smart wire configuration of FIG.8, in accordance with an embodiment;

FIG. 10A is a block diagram of logical couplings of the peer-to-peercommunication network of FIG. 4 in another example smart wireconfiguration, in accordance with an embodiment; and

FIG. 10B is a block diagram of logical couplings of the peer-to-peercommunication network of FIG. 4 in another example smart wireconfiguration, in accordance with an embodiment.

DETAILED DESCRIPTION

When introducing elements of various embodiments of the presentdisclosure, the articles “a,” “an,” “the,” and “said” are intended tomean that there are one or more of the elements. The terms “comprising,”“including,” and “having” are intended to be inclusive and mean thatthere may be additional elements other than the listed elements. One ormore specific embodiments of the present embodiments described hereinwill be described below. In an effort to provide a concise descriptionof these embodiments, all features of an actual implementation may notbe described in the specification. It should be appreciated that in thedevelopment of any such actual implementation, as in any engineering ordesign project, numerous implementation-specific decisions must be madeto achieve the developers' specific goals, such as compliance withsystem-related and business-related constraints, which may vary from oneimplementation to another. Moreover, it should be appreciated that sucha development effort might be complex and time consuming, but wouldnevertheless be a routine undertaking of design, fabrication, andmanufacture for those of ordinary skill having the benefit of thisdisclosure.

The present disclosure is generally directed towards systems and methodsthat may be useful to improve the replacement process associated withthe components and/or the control system of the industrial automationsystem. In particular, methods described herein may use peer-levelcontrol to provide a self-healing, peer-to-peer communication networkwithin an industrial automation system to manage the storage of andaccess to backup device configuration files after a network device losesa device configuration file or is replaced with a device with anincomplete device configuration file.

As mentioned above, industrial automation systems may include automationcontrol and monitoring systems (e.g., industrial control systems). Theautomation control and monitoring systems may monitor statuses and/orreceive information from a wide range of devices, such as valves,electric motors, sensors, other suitable monitoring devices, or thelike. These components may communicate with each other via a suitablenetwork, such as a peer-to-peer communication network. Devices coupledvia a peer-to-peer communication network may be configured according toa device configuration file. The device configuration file may includeprocessing instructions, settings, operating ranges, indications ofconnections to other components within the industrial automation system,or the like, and may be used to customize an operation of devices and/orthe control system to a particular process. However, when a device isoperating offline or is removed (e.g., as part of a replacement) fromthe peer-to-peer communication network, the device configuration filemay be lost or removed from the device and/or may not be transferredautomatically to a replacement device.

In some cases, a configuration manager software may replace theconfiguration of the device and/or control system, thereby increasingtime and processing resources used to prepare the replacement deviceand/or control system for use. Furthermore, an intermediary controlsystem, such as a programmable logic controller (PLC) or a programmablelogic device (PLD), may control communications between components in thepeer-to-peer communication network, including communications between theconfiguration manager software and the network devices. In some cases,the components may manage communications without an intermediary controlsystem by enabling the network devices to directly communicate with eachother. Communication networks that include components configurable tocommunicate without the intermediary control system may be relativelymore resilient to unpredicted or unexpected loss of the control system(e.g., control system unexpectedly going offline) than those with theintermediary control system since the communication network may continueto operate even when the intermediary control system is unusable.

To improve replacement and/or maintenance operations of the peer-to-peernetwork, network devices may store backup device configuration filesassociated with operation of the peer-to-peer communication network.When a device configuration file is lost or removed from a networkdevice of the peer-to-peer network, a peer network device may transmit abackup device configuration file to replace the lost or removed deviceconfiguration file. For example, a first device may store a first deviceconfiguration file defining settings, operations, thresholds, or thelike for the first device while simultaneously storing a second deviceconfiguration file that defines settings, operations, thresholds, or thelike for a second device. If the second device configuration file (e.g.,original device configuration file) stored in the second device waslost, the first device may transmit the second backup deviceconfiguration file (e.g., backup of the original device configurationfile) to the second device for configuration. The redundancy and sharingoperations of the device configuration files between the devices mayoccur independent of an intermediary control system. Redundant deviceconfiguration file storage may further improve a resiliency of thepeer-to-peer communication network to unpredicted or unexpected loss ofthe intermediary control system (e.g., control system unexpectedly goingoffline) since the peer-to-peer network may operate independent of anintermediary control system (e.g., PLC) guiding individual transactionsor communications.

Keeping this in mind, systems and methods that improve management of thepeer-to-peer communication network may include methods that enablediscovery of data endpoints (e.g., recipient device) in response to adevice being installed into the peer-to-peer communication network.Either a receiving device (e.g., data consuming device, consumer) or atransmitting device may perform a discovery operation on thepeer-to-peer communication network. For example, when a receiving deviceis discovered by a transmitting device (e.g., data producing device,producer), the transmitting device may initialize a sub-network (subnet)between the devices, such that a subnet is a portion of a communicationnetwork logically designated for transmitting messages between two ormore network devices. The transmitting device may transmit the deviceconfiguration file to receiving devices via the established subnet. Whena newly installed device into the peer-to-peer communication network isdiscovered, the respective device that discovered the new device mayautomatically transmit the backup device configuration file from therespective device to the newly installed device, thereby initializingthe newly installed device to the peer-to-peer communication network(e.g., reconfiguring the replacement device). A peer-to-peercommunication network that operates to backup device configuration filesmay enable the peer-to-peer communication network to “self-heal” orautomatically reconfigure devices added to the peer-to-peercommunication network to replace a previous network device.

Unlike systems that use an intermediary control system, either thereceiving device or the transmitting device may start a data transactionin the above-described peer-to-peer network. In this way, anintercommunicating device pair may not wait to receive a control signalfrom the intermediary control system to start a data transmission. Thismay improve data communication latencies of the industrial automationsystem since the transmitting devices may transmit data to receivingdevices at will and without latencies associated with an intermediarycontrol system synchronizing communications.

By way of introduction, FIG. 1 is a block diagram of an examplepeer-to-peer communication network (P-P network) 10 that may be employedin an industrial automation system. The P-P network 10 includes networkdevices 12 (12A, 12B, 12C, 12D, 12E). Each of the network devices 12 mayinclude sensing circuitry for monitoring an industrial automationsystem. Sensing circuitry of the network devices 12 may generate outputdata indicative of an operation and/or aspect of the industrialautomation system. For example, a network device 12A may detect when aninput button is pressed, such as to start a motor. Some network devices12 may include sensing circuitry that generates digital or analog valuesrepresentative of a sensed voltage, current, pressure, moisture level,audio level, containment level, or any other suitable parameterassociated with operation of the industrial automation system. Sensingdata resulting from the sensing circuitry may be of any suitable format,and thus may include one or more analog electrical signals, digital datasignals, pulse-width-modulated data signals, or the like. It is notedthat the acquired data may be transmitted via any wired or wirelesscommunication signals, such as radio frequency signals. Network devices12 may also include a variety of scanners, gauges, valves, flow meters,or the like, and may each generate sensing data. Data generated by thenetwork devices 12 may be used in controlling operations of theindustrial automation system, such as by using the data as an input in acontrol loop. In this way, the P-P network 10 may represent a subset orportion of an industrial control network used to manage operations ofthe industrial automation system.

Each of the network devices 12 may receive communication signals and/orpower supply signals from a communication gateway and power supplydevice 14 and/or other network devices 12. The network devices 12 mayuse these supplied signals to perform sensing operations, to transmitoutput operations, or the like. For example, the network device 12B maydetect when a corresponding input button has been pressed as part of astop request, and the network device 12B may use the supplied signalsfrom the communication gateway and power supply device 14 to detect thatthe input button has been pressed when a contact closes, completing anelectrical coupling between the sensing circuitry and a line supplyingan electrical signal from the communication gateway and power supplydevice 14, thereby generating a detectable voltage or current.

One or more of the network devices 12 may couple to a load. For example,the network device 12E may be a motor starter that couples to a motorand controls an operation of the motor based on control signals outputfrom input/output circuitry 16E. Each of the network devices 12 may becoupled to the P-P network via the respective input/output circuitry 16.Each of the network devices 12 may include other input/output circuitryto couple to non-network components (e.g., loads). Data generated by thenetwork devices 12 may be packaged in a message and transmitted tonetwork devices on the P-P network 10 and/or other devices via thecommunication gateway and power supply device 14 through the P-P network10.

The network devices 12 may operate responsive to device configurationfiles. A device configuration file may define processing instructions,settings, operating ranges, indications of connections to othercomponents within the industrial automation system, or the like, and maybe used to customize an operation of devices and/or the control systemto a particular process. In this way, operation of the network devices12 may be define by respectively stored device configuration files. Forexample, the network device 12A may store a first device configurationfile while the network device 12B may store a second deviceconfiguration file different from the first device configuration file.

Sometimes during operation, the network devices 12 may lose the storeddevice configuration file and/or one or more of the network devices 12may be replaced, resulting in a lack of the device configuration file.In this way, the situation may arise in which a device configurationfile may be transmitted to the network device 12 during operation ofand/or after a first initialization of the P-P network 10 (e.g., a firstpower on of the P-P network 10 as may be the case with a devicereplacement operation). Sometimes, a workstation 18 (e.g., computingdevice) running a P-P manager software 20 may transmit a deviceconfiguration file to one of the network devices 12 to initializeoperations of the P-P network 10. For example, the workstation 18 maytransmit a device configuration file to the network device 12A toreconfigure or initialize the network device 12A according to the deviceconfiguration file. However, this process may be lengthy and complicatedsince the P-P manager software 20 may incur processing delays whiletransmitting the device configuration file.

In some cases, however, each network device 12 may store a backup copyof the device configuration files of the P-P network 10. In this way, ifany of the network devices 12 lose the corresponding deviceconfiguration file, a backup copy of the corresponding deviceconfiguration file may be restored to the network device 12 to replacethe missing device configuration file. This process may restore anoriginal operation to an otherwise inoperable network device 12. Forexample, network device 12E may receive a backup configuration file fromthe network device 12A to restore a lost device configuration file.

To provide a particular example, FIG. 2 is a block diagram of an exampleindustrial automation system 30 including at least a portion of the P-Pnetwork 10. The P-P network 10 may couple to an industrial controlsystem 32 and/or be a part of the industrial control system 32. In thisexample, the network devices 12 are communicatively coupled as part of amotor starter system. The network device 12E is a motor starter 34electrically and communicatively coupled to a motor load 36. The motorstarter 34 may control the powering on, powering off, and operationalcharacteristics of the motor load 36 via control signals. The motorstarter 34 may generate the control signals based at least in part oncontrol signals and/or messages from the network devices 12A, 12B or theindustrial control system 32 via a motor starter control system 38(e.g., network device 12G that uses input/output circuitry 16G). Themotor load 36 is merely one example of a load of the P-P network 10.Clearly, for other applications, the particular system, machinecomponents, machines, stations, and/or conveyors may be different orspecially adapted to the application. In addition to the equipmentdescribed above, the industrial automation system may also includeadditional motors, protection devices, switchgear, compressors, and thelike.

For example, the motor starter 34 may power on the motor load 36 inresponse to a message from the network device 12A, a start button 40.The start button 40 may be an input device that enables an operator toprovide a control instructions (e.g., start or power on, stop or poweroff) to the motor starter 34. The network device 12C, a status pilotlight 42, may emit light in response to a message from the motor starter34 indicative of an operation of the motor load 36. Each of the networkdevices 12 may provide messages to the communication gateway and powersupply device 14 and/or to the human/machine interface (HMI) 44. In thisway, the HMI 44 may provide visual statuses and/or notifications to anoperator of the example industrial automation system 30.

The HMI 44 may operate as an operator interface to permit the operatorto provide control instructions to the network devices 12. Theindustrial control system 32 may represent components of the industrialautomation system 30, and operations and/or current statuses of thecomponents, through visualizations of components and/or network deviceson the HMI 44. An operator monitoring the industrial automation system30 may refer to the HMI 44 to determine a current operation of theindustrial automation system 30 when adjusting an operation of theindustrial automation system 30 and/or for a particular component.

The motor starter 34, as an example, may operate according to a deviceconfiguration file 46. Copies of the device configuration file 46 may bestored as a backup device configuration files 48 (48A, 48D) in thenetwork devices 12. In some embodiments, the network devices 12 may eachreceive a backup device configuration file 48 for each of the othernetwork devices. For example, although network device 12E is notdirectly adjacent to network device 12A, network device 12A may stillreceive a backup device configuration file 48B for the network device12E. In this way, each of the network devices 12 may store a deviceconfiguration file 46 and one or more backup device configuration files48. The backup device configuration files 48 may be used to restore aconfiguration to the motor starter 34 in the event that something causesthe motor starter 34 to lose the device configuration file 46, such as adata loss event or a device replacement. For example, a data loss eventmay cause the motor starter 34 to lose or remove the deviceconfiguration file 46. Additionally or alternatively, a devicereplacement may involve replacing an original motor starter 34 with areplacement motor starter 34 that does not have the device configurationfile 46 stored therein. In either of these cases, one of the backupdevice configuration files 48 may be used to restore the deviceconfiguration file 46 to the motor starter 34.

To restore the device configuration file 46 to the motor starter 34,each network device 12 may detect when the network devices 12E goesoffline and/or loses the stored device configuration file 46. Forexample, when the motor starter 34 goes offline from the P-P network 10,the other network devices 12A, 12B, 12C, 12D may detect this, maydetermine when the motor starter 34 is powered on again or is otherwiseready to receive the backup device configuration file 48, and maytransmit the backup device configuration file 48 to the motor starter 34to restore the original device configuration file 46 when suitable. Inthis way, each network device 12 may include a local control system thatmay detect the statuses (e.g., online or offline status) of the othernetwork devices 12.

The local control system and/or any of the network devices 12 maydetermine when one of the network devices 12 is online or offline byperforming any suitable type of detection operation. Detectionoperations may include each of the network devices 12 regularlytransmitting a signal that is tracked, such that when a threshold numberof signals are missed or not detected, a respective of the networkdevices 12 may be identified as offline or missing. For example, thenetwork device 12E may transmit, at a regular or equal time interval, asignal to the network device 12A. The network device 12A may monitor forthe signal and if the time interval were to pass without the networkdevice 12A receiving the signal, a count may be adjusted (e.g.,incremented, decremented) to reflect the missed signal. After the countreaches a threshold number, the network device 12A may determine thenetwork device 12E to be offline or missing the device configurationfile 46.

An example of a local control system is shown in FIG. 3. FIG. 3 is ablock diagram of an example local control system 64 used to perform oneor more of the operations described herein. Each of the network devices12 may include a respective local control system 64. By way of example,the local control system 64 may include a communication component 66, aprocessor 68, a memory 70, input/output (I/O) ports 72, or the like. Thecommunication component 66 may be a wireless or wired communicationcomponent that may facilitate communication between the industrialautomation components, the industrial control system, and othercommunication capable devices. Although depicted as coupled to othercomponents of the industrial control system, it should be understoodthat one or more local control systems 64 may be associated with anycomponent of the industrial control system. The communication component66 and the I/O ports 72 may be considered interface circuitry 74.

The processor 68 may be any type of computer processor or microprocessorcapable of executing computer-executable code. The processor 68 may alsoinclude multiple processors that may perform the operations describedbelow. The memory 70 may be any suitable article of manufacture thatserves as media to store processor-executable code, data, or the like.These articles of manufacture may represent computer-readable media(e.g., any suitable form of memory or storage) that may store theprocessor-executable code used by the processor 68 to perform thepresently disclosed techniques. Generally, the processor 68 may executesoftware applications that include programs that enable a user to trackand/or monitor operations of the industrial automation components via alocal or remote communication link.

The memory 70 may also store the data, analysis of the data, thesoftware applications, and the like. The memory 70 may representnon-transitory computer-readable media (e.g., any suitable form ofmemory or storage) that may store the processor-executable code used bythe processor 68 to perform various techniques described herein. In oneembodiment, the memory 70 may include a software application executed bythe processor 68 and used to monitor, control, access, or viewindustrial automation equipment. The memory 70 may be used to store thedevice configuration file 46 or the backup device configuration file 48.

The I/O ports 72 may be interfaces that may couple to other peripheralcomponents such as input devices, sensors, I/O modules, and the like.I/O ports 72 may enable the local control system 64 to communicate withthe industrial automation equipment or other devices in the industrialautomation system. In certain embodiments, the local control system 64includes and/or couples to various other sensors that may provideadditional data related to an ambient environment of the network devices12 and/or the operation of the industrial automation system. Forinstance, the other sensors may include an accelerometer, a gas (e.g.,smoke, carbon monoxide) sensor, or the like.

To elaborate on self-healing operations of the P-P network 10, FIG. 4 isa block diagram representation of a state of the P-P network 10 after adevice replacement operation. During a normal operation of the P-Pnetwork 10, each of the network devices 12 may communicate (via paths84) with each other. For example, the network device 12A may transmit amessage to the network device 12E that indicates a start instruction. Asanother example, the network device 12E may transmit a message to thenetwork device 12C that indicates a motor load state.

One or more of the network devices 12 may intercommunicate viasub-networks (subnets) of a communication network 86. The communicationnetwork 86 may be a smart wire configuration that enables the networkdevices 12 to couple to the communication network 86 at the input/outputcircuitry 16. Examples of the smart wire configuration may be shown viaFIG. 8, FIG. 9, FIG. 10A, and/or FIG. 10B. Each of the network devices12 may transmit or receive messages via subnets of the communicationnetwork 86. For example, a subnet may guide transmission of data fromthe network device 12E to the network device 12C and/or from the networkdevice 12A to the network device 12E. Subnets may be logically separatedchannels of the communication network 86, such that a same network maytransmit data via the respective subnets without interruption tosimultaneous transmissions. The communication network 86 may be of anysuitable network, including wireless networks or wired networks, such asan Ethernet-based network. Each network device 12 may be considered atransmitting device and/or a receiving device. Some of the networkdevices 12 may operate as both a transmitting and a receiving device.The network devices 12 may transmit messages via respective subnetswithout assistance, or without being in response to a control signalfrom, an intermediary control system. To do so, the network device 12may reference the device configuration file 46 stored in the memory 70to determine which subnet to use to transmit a generated message. Forexample, the network device 12E may reference its own deviceconfiguration file 46 to determine which subnet and which other of thenetworked devices 12 to send the generated message. Subnet definitionsmay be based at least in part on what operation was used to determinethe data for the generated message. In this way, different operations ofthe same network device 12 may use different subnets to transmit data.Adjacent devices may also be bypassed during data transmissions usingthe subnets since the data may be transmitted through the input/outputcircuitry 16 without being received at the within the network device 12.

The network device 12 may use one or more identifiers included with thegenerated message to indicate to routing circuitry and/or tointercommunicating network devices an intended destination of themessage (e.g., data endpoint) and through which subnet to transmit themessage. Messages transmitted between a first network device 12 and asecond network device 12 via a first subnet may not be interrupted by amessage transmission between a third network device 12 and a fourthnetwork device 12 via a second subnet since the communications may beseparated by logical divisions according to the subnets. For example, amessage transmitted via subnet between network device 12A and networkdevice 12E is not interrupted by a message transmitted between networkdevice 12A and network device 12B and/or between network device 12C andnetwork device 12E. Communicating via subnets may improve communicationnetwork operation by permitting one or more network devices 12 tointercommunicate without use of an intermediary control system to managethe communications.

The device configuration file 46 may assign a network device to asubnet. In this way, two network devices 12 assigned to the same subnetmay intercommunicate via the subnet without communicating via anadditional subnet. Each network device 12 may communicate via a varietyof subnets that connect one or more network devices 12. For example, thenetwork device 12E may communicate with the network device 12A through afirst subset and may communicate with the network device 12B through asecond subnet without use of an intermediary control system to managethe data transmissions.

A message generated by a network device 12 may be identified via aheader before or after payload data of the message (e.g., sensing data,control operation, status). The header may include data regarding anoriginating network device 12 of the message, a destination of themessage, and a subnet through which to transmit the message. Routingcircuitry, such as routing circuitry of the P-P network 10 and/or of theinput/output circuitry 16, may interpret the header to determine how totransmit the message through the communication network, and, inparticular, the subnet through which to transmit the message. Sincesubnet definitions may be included in a device configuration file,loading the device configuration file to configure a device of thepeer-to-peer communication network may initialize and set (e.g.,establish, logically define) communication pathways between the networkdevices 12.

Sometimes during operation of the industrial automation system 30, anetwork device 12 is to be replaced. This is represented in FIG. 4 asthe network device 12F being replaced by the network device 12E. Whenthe network device 12E replaces the network device 12F, a deviceconfiguration file 46 defining the operation of the network device 12Fmay be stored on to the network device 12E. However, in the P-P network10 that is able to perform self-healing operations, the network devices12A, 12B, 12C, 12D may automatically identify when the network device12F is replaced and may automatically transmit a backup deviceconfiguration file 48 to the replacement network device 12E withoutoperator intervention or intermediary control system intervention.

For example, the network devices 12A, 12B, 12C, 12D may determine whenone of the other network devices 12F is online or offline by performingdetection operations as briefly mentioned above. Detection operationsmay include each of the network devices 12 broadcasting a signalparticularly assigned to the respective network device 12 to bemonitored, such that when a threshold number of signals are missed ornot detected, a respective of the network devices 12 may be identifiedas offline or missing. For example, the network device 12A may transmita signal to the network device 12E at a regular or equal time interval.The network device 12E may monitor for the signal and if the timeinterval were to pass without the network device 12E receiving thesignal, a count may be adjusted (e.g., incremented, decremented) toreflect the missed signal. After the count reaches a threshold number,the network device 12E may determine the network device 12A to beoffline or missing. In some cases, a continuous status signal may betransmitted to the P-P network 10 by each of the network devices 12,such that when one of the continuous status signals disappears, each ofthe other network devices 12 that are still online are able to determinewhich of the network devices 12 went offline.

To perform the self-healing operation, for example, the network device12A storing a backup device configuration file 48 may try to transmitthe backup device configuration file 48 to the replacement networkdevice 12E. If that transmission is incomplete or unable to happen, anext network device 12, such as the network device 12B, may try totransmit the backup device configuration file 48 to the replacementnetwork device 12E. Attempting to transmit the backup deviceconfiguration file 48 may be repeated until a network device 12 havingthe appropriate backup device configuration file 48 completes thetransmission.

It is noted that each network device 12 of the P-P network 10 mayperform the self-healing operations. For example, network device 12A maystore a device configuration file 46 defining operation of the networkdevice 12A, in addition to one or more other backup device configurationfiles 48 for other network devices 12 of the network. This may apply toeach network device 12 of the P-P network 10.

Each backup device configuration file 48 may include information used bythe network device 12 to perform control operations and/or tointercommunicate via the P-P network 10. The backup device configurationfile 48 may mirror a device configuration file 46 for a particularorigin device (e.g., network device 12 storing the backed up andoriginal device configuration file 46). Since a device configurationfile 46 stores information associated with operations of the networkdevice 12, the device configuration file 46, and thus the backup deviceconfiguration file 48, may include an origin device configurationidentifier, origin device P-P network configuration data, and/or anorigin device P-P network configuration data cyclic redundancy checkvalue (CRC value).

The origin device configuration identifier may include a device address,a position identifier, and/or a device product key. The device addressmay be a logical address used to identify the originating network device12 for the purposes of message transmission. In this way, the deviceaddress may be interpretable by the communication network 86, such asvia routers or routing circuitry of the communication network 86. Theposition identifier may identify a logical position relative to othernetwork devices 12. For example, the position identifier of networkdevice 12A may indicate numerically that the network device 12A isadjacent to network device 12B and network device 12E. The deviceproduct key may identify the particular network device 12 from aperspective of manufacturing. For example, the device product key of thenetwork device 12A may indicate a model, make, year manufactured, and/oroperational features of the network device 12A and, in some cases, maydifferentiate the network device 12A from a similarly manufacturednetwork device. The origin device configuration identifier may enablethe network devices 12 to identify the origin device corresponding tothe device configuration file 46. Furthermore, the origin deviceconfiguration identifier may be used to match a new device to storedbackup device configuration file 48 via matching of device product keys.The new device may be an unconfigured network device. When the newdevice is matched to a backup device configuration file 48, one of thenetwork devices 12 may transmit the backup device configuration file 48to the new device to bring the new device online (e.g., to turn the newdevice into a network device 12).

The backup device configuration file 48 may also include origin deviceP-P network configuration data. The origin device P-P networkconfiguration data may define processing instructions, settings,operating ranges, indications of connections to other components withinthe industrial automation system, or the like, and may be used tocustomize an operation of the network device 12 to the P-P network 10and/or to the industrial automation system 30. For example, the origindevice P-P network configuration data may define at what frequency anetwork device 12 is to sample information, communicate statuses withother network devices 12, update an output from the I/O ports 72, suchas a control signal to perform an operation or to communication astatus, or the like.

The backup device configuration file 48 may also include the CRC value.The CRC value may be generated when an encryption and/or encoding of thebackup device configuration file 48 occurs, such as in preparation fortransmission via the P-P network 10. The CRC value may be one or morebits, or character strings, included with a device configuration file 46and/or a backup device configuration file 48. The CRC value may be usedto verify whether a data transmission involving the device configurationfile 46 and/or the backup device configuration file 48 is secure and/orperformed without comprise to the original data of the deviceconfiguration file 46 and/or the backup device configuration file 48(e.g., was transmitted without unintentional or intentionalmanipulation). Encryption and/or security operations may use the CRCvalue when verifying whether unauthorized access attempts are performedto the P-P network 10 and/or any of the network devices 12.

In some embodiments, the new device may retrieve the backup deviceconfiguration file 48 from the network device 12. For example, the newdevice may send a request to the network devices 12 in the P-P network10 with the device configuration identifier of the new device. The firstnetwork device 12 that has a matching backup device configuration file48 that includes an origin device configuration identifier that matchesthe device configuration identifier may report back to the new device.The new device may receive the backup device configuration file 48 fromthe network device 12 with the matched origin device configurationidentifier. Then, the new device may store the backup deviceconfiguration file 48 as the device configuration file 46.

Determining which network device 12 is to transmit the backup deviceconfiguration file 48 (e.g., determining a restoring network device 12)may be based on a date and/or time of the data stored, ongoingoperations, a physical proximity, a logical proximity, or the like. Whenusing a date and/or time of data stored, the backup device configurationfile 48 that corresponds to a most recent update may be used to restorethe configuration file to the new device. Furthermore, when ongoingoperations are used to select a copy of the backup device configurationfile 48, a candidate restoring network device 12 involved in ongoingoperations may not be selected to transmit the backup deviceconfiguration file 48. For example, if network device 12A is missing adevice configuration file 46 but network device 12B is involved in anongoing operation and is unavailable to transmit the backup deviceconfiguration file 48, the network device 12C or the network device 12Dmay transmit the backup device configuration file 48 to the networkdevice 12. This may reduce delays caused by waiting for a network device12 to be available to transmit a backup device configuration file 48.

When using physical proximity as a condition upon which to determine therestoring network device 12 (e.g., the network device 12 that is to beused to restore the original device configuration file 46 to the newdevice based on the backup device configuration file 48), the networkdevices 12 may determine a physical distance associated withcommunication channels of the P-P network 10. The physical distance maybe determined based on a difference in locations between network devices12. For example, a distance may be determined between the new networkdevice 12E and a candidate restoring network device 12A (e.g., one ofthe network devices 12A, 12B, 12C, 12D being considered to become therestoring network device 12). The pair of devices that has the lowestrelative physical distance may be selected (e.g., as a way to loweroverall communication time or reduce transmission latencies). When usinglogical proximity, a similar comparison to physical proximity may beperformed but via a comparison that uses logical locations and/or alogical proximity between the new device and the candidate restoringnetwork device 12. For example, the network device 12A may determinethat the network device 12B has lost the device configuration file 46.The network device 12A may determine which of the network devices 12 isof closer logical proximity to the network device 12B. The networkdevice 12A may determine that the network device 12D is logically closerto the network device 12B than the network device 12A. The determinationof logical proximity may include evaluating subnet routings betweennetwork devices 12 and/or anticipated memory retrieval latencies todetermine a more efficient logical transmission route relative topossible logical transmission routes.

The network devices 12 may use combination of conditions (e.g., physicalproximity, a logical proximity, a date and/or time of the data stored,ongoing operations) to identify the restoring network device 12. Forexample, a backup device configuration file 48 corresponding to the mostrecently obtained or stored data that is also physically closest to thenew network device 12E may be used to restore the configuration to thenew device, such as the backup device configuration file 48 stored inthe network device 12A. In this way, a combination of tradeoffs may beconsidered when determining the identifying network device 12.

Each of the network devices 12 may be a static transmitting device, astatic receiving device, a dynamic transmitting device, a dynamicreceiving device, or any combination thereof. A static transmittingdevice may generate a message that includes a option selected from afixed set of options (e.g., on or off, high or low, yes or no), while astatic receiving device may interpret a message to generate an outputfrom a fixed set of options. Each static device may have a fixed set ofdata options, where the data may be binary data and/or analog data. Adynamic transmitting device may generate a message that includes datafrom a variable set of options (e.g., a value that changes in responseto an input not part of a defined set of options), while a dynamicreceiving device may receive one or more messages and use data of themessages to generate an output. Each dynamic device may have adynamically generated variable set of data options according to aspecific operation. The data associated with the dynamic device may bebinary or analog.

For example, network device 12A may be a static transmitting devicesince the network device 12A may generate a message indicating when thestart button 40 is pressed but may not generate a message indicatingintermediating positions of the start button 40 or indicating at whatrelative location the button is pressed. On the other hand, a networkdevice 12 that includes a pressure sensor may generate a message thatincludes data corresponding to a non-binary set of options since thepressure sensor may transmit a message based on a relative indication ofpressure within a vessel, and not necessarily in response to pressurebeing present in the vessel in general.

A communicative coupling between one or more static transmitting devicesand one or more static receiving devices may be made via a hardcodedlocal control and/or via a programmable logic control, as defined viathe device configuration file 46. The hardcoded local control mayinclude use a hardcoded subnet definition defining the transmittingdevices and defining the receiving devices (e.g., hardcoded in a deviceconfiguration file 46). Hardcoded local control may use physicalcouplings to define sub-networks and/or transmission pathways. Theprogrammable logic control may include one or more determinations to seta receiving network device 12. For example, in a programmable logiccontrol system, a transmitting network device 12 may determine to whichreceiving device to transmit based at least in part on the generatedmessage and/or generated data before transmission. Sometimes the deviceconfiguration file 46 specifics a coordinated local control system forcontrolling communications between any device type, such as betweendynamic transmitting device and static receiving devices, dynamictransmitting device and dynamic receiving devices, or the like. In acoordinated local control system, network devices 12 may process inputsand/or outputs before transmitting data via the P-P network 10. Forexample, a first network device 12 may generate an analog data-basedstatus to be transmitted to a second network device 12 forinterpretation and use in controlling a motor speed but the transmissionmay include a third network device 12 that changes a color of a lightproportional to the value of the analog data-based status from the firstnetwork device 12 before transmission onto the second network device 12.As an additional example, the network device 12D may generate a messagethat a second network device 12E uses to determine a third of thenetwork devices 12 to transmit the message.

To help describe operations of the P-P network 10, FIG. 5 is a flowchartof a method 100 for transmitting a device configuration file 46 via theP-P network 10. Although the method 100 is described as being performedby a network device 12, it should be understood that the method 100 maybe performed by any suitable component of the P-P network 10. Forexample, any network device 12, the industrial control system 32, or anysuitable processing circuitry may perform some or all of the method 100.The method 100 may be performed to initialize a network device 12. Asdescribed below, particular network devices 12 are called out in thedescriptions of the method 100. It is noted that this is done for easeof discussion, and in an actual implementation, the operations describedherein may be interchangeable between the network devices 12.

At block 102, the network device 12F may discover other network devices12A, 12B, 12C, 12D present on the P-P network 10. One or more of thenetwork devices 12 that operate as part of the P-P network 10 may beconsidered a P-P data endpoint. The network device 12F may perform asearch of the P-P network 10 to detect the P-P data endpoints. Thecommunicative couplings of the P-P network 10 may enable the networkdevice 12F to detect connection statuses of the other network devices12A, 12B, 12C, 12D (e.g., whether or not the other network devices 12A,12B, 12C, 12D are coupled and/or communicating via the P-P network 10).

At block 104, the network device 12F may generate a device configurationfile 46 at least in part by defining subnets. Based on controloperations to be performed by the network device 12F and the discoverednetwork devices 12A, 12B, 12C, 12D, the network device 12F may determinewhich of the discovered network devices 12A, 12B, 12C, 12D that datagenerated by the network device 12F is to be transmitted, and thus whichgroups of network devices 12A, 12B, 12C, 12D are associated with eachother or with the network device 12F. In this way, the network device12F may define a subnet between receiving network devices 12 andtransmitting network devices 12 determined to be associated with eachother. The device configuration file 46 may be a configuration fileinitially installed on the network device 12F that the network device12F updates to include definitions of the subnets (e.g., at a later timethan initial installation) and/or updates to one or more settings.

After subnet definitions are included in the device configuration file46, at block 106, the network device 12F may transmit the deviceconfiguration file 46 to one or more other network devices 12A, 12B,12C, 12D as the backup device configuration file 48. The backup deviceconfiguration file 48 may be used to restore an original configurationto the network device 12F in the event that the network device 12F isreplaced with a new device (presumably a new device without the originaldevice configuration file 46 stored).

When the network device 12F is replaced, one of the other networkdevices 12A, 12B, 12C, 12D may detect the replacement and facilitate thetransmission of the backup device configuration file 48 to restore aprevious operational capacity of the replaced network device 12F to anew network device 12E. This process is described by FIG. 6.

FIG. 6 is a flowchart of a method 120 for performing a replacement of adevice configuration file 46. Although the method 120 is described asbeing performed by a network device 12, it should be understood that themethod 120 may be performed by any suitable component of the P-P network10. For example, any network device 12, the industrial control system32, or any suitable processing circuitry may perform some or all of themethod 120. The method 120 may be performed in response to the networkdevice 12 detecting a new device being coupled to the P-P network 10. Insome cases, the network device 12 may detect a new device beinghot-swapped, or physically replaced while the P-P network 10 remainsonline. As described below, particular network devices 12 are called outin the descriptions of the method 120. It is noted that this is done forease of discussion, and in an actual implementation, the operationsdescribed herein may be interchangeable between the network devices 12.

At block 122, one of the network devices 12A, 12B, 12C, 12D maydetermine that a new network device 12E is installed into the P-Pnetwork 10. A newly installed network device 12E may broadcast a signalvia the P-P network 10 for the other network devices 12A, 12B, 12C, 12Dto detect and interpret as a notification message from the newlyinstalled network device 12E confirming installation. Additionally oralternatively, one of the network devices 12A, 12B, 12C, 12D maydetermine that a new network device 12E is installed into the P-Pnetwork 10 by polling the P-P network 10 to detect when the networkdevice 12E is installed. Signals used to poll the P-P network 10 may betransmitted by one or more of the network devices 12A, 12B, 12C, 12D ona periodic frequency to regularly check for newly installed devices.Although, the new network device 12E may not be initially able tocommunicate via the P-P network 10, the new network device 12E may bephysically coupled to the P-P network 10. For ease of discussion,network device 12C is described below as detecting the installation ofthe network device 12E.

In response to determining that the new network device 12E is installedinto the P-P network 10, the network device 12C, at block 124, may sendthe backup device configuration file 48 to the new network device 12E.The backup device configuration file 48 corresponds to a deviceconfiguration file 46 of the previously installed network device 12F(e.g., the network device 12 that was replaced). The backup deviceconfiguration file 48 may restore settings, operations, and/orthresholds to be referenced by the new network device 12E whenperforming control operations (e.g., executing local control operationsto generate an output from the new network device 12E in response to aninput into the new network device 12E). The backup device configurationfile 48 may also define a subnet to which certain outputs are to becommunicated on by the new network device 12E.

At block 126, the network device 12C may receive a message from the newnetwork device 12E based at least in part on a mutual setting of thebackup device configuration file 48 defining a subnet (e.g., now storedas the device configuration file 46 within the new network device 12E).In some cases, the mutual setting may correspond to a type of device tobe a data endpoint for data generated by a particular control operation.The network device 12C may be defined as a data endpoint for a controloperation of the new network device 12E. Thus, the new network device12E may transmit data generated via the control operation to the networkdevice 12C, when the data is ready for transmission in a message.

At block 128, the network device 12C may execute a local controloperation using the data received via the message from the new networkdevice 12E. In this way, the network device 12C performs an operationbased on results from an operation of the new network device 12E. Forexample, the new network device 12E may output a status indicating aload is powered on and the network device 12C may cause a light-emittingdevice to emit light in response to receiving data indicating that theload is powered on from the new network device 12C. A variety ofsuitable control operations may be performed by one or more networkdevices 12 in response to various inputs and/or outputs from the othernetwork devices 12.

In some embodiments, the P-P network 10 may include an intermediarycontrol system. The intermediary control system may managecommunications between network devices 12. However, in these systems,the network device 12 may be able to perform autonomously withoutinstruction from the intermediary control system at least in part byusing the systems and methods described herein. For example, if theintermediary control system were to be taken offline, the P-P network 10may be resilient and may continue to operate using subnet communicationsbetween the network devices 12 and/or may continue to operate inresponse to messages generated via a transmitting network device 12. Inthis way, the control mode (e.g., intermediary control systemoperational mode versus local control operational mode via the networkdevices 12) may be either selected by an operator (e.g., a mode manualselection) or may be automatically selected by the P-P network 10 (e.g.,mode automatic selection) in response to the network devices 12detecting an offline or unusable intermediary control system. In eithercase, the intermediary control system operational mode or the localcontrol operational mode may be selected via a control signalconfigurable to switch a switching device, thereby causing the P-Pnetwork 10 to enter the operational mode. Additionally or alternatively,the operational mode of the P-P network 10 may be set via an internalparameter controlled by software of the industrial control system 32.When the switching between the operational modes is automatic, aswitching condition may be a network status. For example, the P-Pnetwork 10 may be switched into the mode automatic selection in responseto a status of a communicative coupling between one or more networkdevices 12 and the intermediary control system.

FIG. 7 is a flowchart of a method 140 for generating a deviceconfiguration file 46 and a backup device configuration file 48 using anintermediary control system. Although the method 140 is described asbeing performed by an intermediary control system, it should beunderstood that some or all the method 140 may be performed by anysuitable component of the P-P network 10, including a network device 12facilitating the generation of a device configuration file 46 or abackup device configuration file 48. The method 140 may be performed inresponse to one of the network devices 12, industrial control system 32,the intermediary control system, or any suitable processing device,detecting a new device being coupled to the P-P network 10. In somecases, the intermediary control system may detect a new device beinghot-swapped, or physically replaced while the P-P network 10 remainsonline. As described below, particular network devices 12 are called outin the descriptions of the method 140. It is noted that this is done forease of discussion, and in an actual implementation, the operationsdescribed herein may be interchangeable between the network devices 12.

At block 142, the intermediary control system may discover dataendpoints. When performing discovery operations, the intermediarycontrol system may use test control signals to track which networkdevices 12 are coupled to the P-P network 10. As part of the discoveryoperations, the intermediary control system may determine which networkdevices 12 are adjacent to each other and may use that information whenpairing a transmitting network device 12 with a receiving network device12.

At block 144, the intermediary control system may generate a deviceconfiguration file 46 by associating the data endpoints based on a localcontrol application. The intermediary control system may store or mayretrieve the local control application from memory 70. The local controlapplication may include control and/or operational definitions for eachof the network devices 12. The control and/or operational definitionsmay include definitions for operating frequencies, transmissionprotocols, conversion polices, or the like, to enable communicationbetween two network devices 12 and the P-P network 10. For example, thenetwork device 12A may operate according to operational definitions of acorresponding local control application. The intermediary control systemmay generate the device configuration file 46 to include starting points(e.g., device origins) and endpoints for each local control applicationof the network device 12A. If, for example, the network device 12Aoutputs a control signal to network device 12E in response to datagenerated by the network device 12A and data received from the networkdevice 12D, the local control application may define a particularfrequency at which the network device 12A is to expect to receive datafrom the network device 12D, a particular frequency at which the networkdevice 12A is to poll its own sensing devices to receive generatedsensing data, and a particular frequency at which the network device 12Ais to compare data from the network device 12A and its own generatedsensing data to determine the control signal output to the networkdevice 12E. In this example, the starting points of the local controlapplication include the network device 12D and the network device 12A,while the data endpoint of the local control application is the networkdevice 12E. In this way, to generate the device configuration file 46,the intermediary control system may, for example, determine a controloperation to be performed by the network device 12A based on a localcontrol application.

The intermediary control system may determine from the local controlapplication a type of device to receive data that is going to begenerated and transmitted by the network device 12A. The local controlapplication may define the type of device using the device product key(or a subset of the device product key, such as a string correspondingto a model number or part type). Once the type of device is determined,the intermediary control system may determine which of the networkdevices 12 corresponds to the type of device. In this example, theintermediary control system may determine that the network device 12Ematches the type of device. This may be determined by matching the typeof device to one or more of the device product keys of the networkdevices 12. The intermediary control system may update a deviceconfiguration file for the network device 12E to reflect a data endpointpairing between the network device 12E and the network device 12A for aparticular data generation operation. The network device 12E and thenetwork device 12A may be defined to intercommunicate via a subnetcoupling since the two network devices 12 are associated with a dataendpoint pairing. After updating the device configuration file 46, thenetwork device 12E may reference the data endpoint pairing to determinethe subnet through which to transmit data generated via the datageneration operation.

At block 146, the intermediary control system may transmit the deviceconfiguration file 46 to a first network device for use in the localcontrol application. In response to receiving the device configurationfile 46, the network device 12 may configure certain settings,thresholds, ranges, subnets, or the like, defined by the deviceconfiguration file 46. After configuration, the network device 12 mayreference the information of the device configuration file 46 whendetermining to perform a local control operation and/or while performingthe local control operation.

At block 148, the intermediary control system may transmit the deviceconfiguration file 46 as a backup device configuration file 48 to asecond network device of the network devices 12 for use in automaticallyreconfiguring a replacement of the network device 12 that receives thedevice configuration file 46. For example, the intermediary controlsystem may transmit the device configuration file 46 to the networkdevice 12A and the backup device configuration file 48 to the networkdevice 12B. In some cases, the intermediary control system may transmitthe backup device configuration file to the network device 12B, 12C,12D, and 12E in response to generating the device configuration file 46to the network device 12A. In this way, each of the network devices 12may store a backup device configuration file 48 for each of the othernetwork devices 12. Transmission of the device configuration file 46 andthe backup device configuration file 48 may happen at the same time, ata partially overlapping time, during different time periods, or anycombination thereof.

In some embodiments, the original device configuration file is generatedby the P-P manager software 20. The P-P manager software 20 may performthe discovery operation of block 102 of the method 100, and update theoriginal device configuration file with the subnet definitions asperformed in the operations of block 104. In this way, block 106 of themethod 100 may refer to, in these cases, the P-P manager software 20transmitting the updated original device configuration file to a firstnetwork device 12 as the device configuration file 46 and to othernetwork devices 12 as the backup device configuration file 48.

As described previously, the network devices 12 may communicate via thecommunication network 86 in a smart wire configuration. FIG. 8 is ablock diagram of the communication network in a smart wire configurationthat enables each of the network devices 12 to directly communicate witheach other without intervention or control by a larger control system.Each network device 12 may generate messages based on operationsperformed by the processors 68. In response to generating the message, anetwork device 12 may transmit the message to another of the networkdevices 12 via a smart wire media infrastructure 160 that includes theinput/output circuitry 16 and the communication network 86. In thisexample, each of the input/output circuitry 16 couples to the smart wiremedia infrastructure 160 via seven pins and seven couplings, however itis noted that any suitable number of couplings may be used to transmitdata between the network devices 16. The interface circuitry 74 maycouple to the input/output circuitry 16 using eight pins or eightcouplings.

The network devices 12 may transmit messages through the smart wiremedia infrastructure 160. The messages transmitted may be passed throughone or more input/output circuitries 16 before reaching a destinationinput/output circuitry 16. For example, input/output circuitry 16E maypass a message to the input/output circuitry 16C from the communicationgateway and power supply 14 without alteration.

FIG. 9 is a block diagram of example logical couplings of the smart wiremedia infrastructure 160A. Each network device 12 may couple to theother network devices 12 via the communication network 86. Controlsignals that enable communication between the network devices 12 includea select signal 172, a network power positive signal 174 and negativesignal 176, an Ethernet positive signal 178 and negative signal 180, anda control power positive signal 182 and negative signal 184. The selectsignal 172 may be a sequential service delivery signal that enables thenetwork devices 12 to transmit messages sequentially through the othernetwork devices 12. The network power positive signal 174 and negativesignal 176 may delivery power to each of the network devices 12 and/orto the network components of each network device 12 from a power supplyor tapped connection off of another electrical coupling. The Ethernetpositive signal 178 and negative signal 180 provide for networkcommunication functionality. The Ethernet positive signal 178 andnegative signal 180 may be a part of a bus and/or multi-drop topology, atopology where multiple data endpoints couple to a same communicationbus. The control power positive signal 182 and negative signal 184 maypower an actuator (e.g., a contactor coil) for at least one of thenetwork devices 12. An actuator may execute a control operation for thenetwork device 12. For example, a control operation of the networkdevice 12E may including transmitting a control signal to the motor 36to power on the motor 36 and an actuator of the network device 12E mayclose to initiate transmission of the control signal.

Several variations of the smart wire media infrastructure 160A are shownin FIG. 10A and FIG. 10B. While the smart wire media infrastructure 160Amay use a seven-line, eight-pin connector to couple the network devices12 to the communication network 86, FIG. 10A and FIG. 10B show that anysuitable number of pins and lines may be used to provide a smart wirecommunication system.

Keeping this in mind, FIG. 10A is a block diagram of another examplelogical couplings of a smart wire media infrastructure 160B and FIG. 10Bis a block diagram of an example logical couplings of a smart wire mediainfrastructure 160C. The smart wire media infrastructure 160B may be afive-line cable that uses six-pin connector circuitry to couple thenetwork devices 12 to the communication network 86. The smart wire mediainfrastructure 160C may be a six-line cable that uses eight-pinconnector circuitry to couple the network devices 12 to thecommunication network 86.

The smart wire media infrastructure 160B combines the network powerpositive signal 174 and the Ethernet positive signal 178 into a samecommunicative coupling. The smart wire media infrastructure 160B alsocombines the network power negative signal 176 and the Ethernet negativesignal 180 into a same communicative coupling. In this way, the networkpower and the Ethernet couplings may share a same pair of wires. Theselect signal 172 may be of a daisy chain configuration, where eachnetwork device 12 is coupled to the adjacent network devices 12.

The smart wire media infrastructure 160C may daisy chain adjacentnetwork devices 12 using the Ethernet positive signal 178 and theEthernet negative signal 180. The Ethernet signals may transmit throughrespective switches 190 of the network devices that may control a timingused to transmit messages between network devices 12 via the Ethernetcommunicative couplings. The network power positive signal 174, networkpower negative signal 176, control power positive signal 182, andcontrol power negative signal 184 of the smart wire media infrastructure160C may operate similar to the same signals of the smart wire mediainfrastructure 160A.

Technical effects of the present disclosure include improving controloperations of an industrial control system through use of networkdevices coupled in a peer-to-peer communication network. The networkdevices may intercommunicate independently of a control system via thepeer-to-peer communication network. In this way, messages transmittedbetween the network devices may incur relatively less latencies and/ormay transmit relatively faster since the network devices are not waitingfor control signals from the control system to operate. Furthermore,network devices of the peer-to-peer network may backup deviceconfiguration files for the other network devices of the peer-to-peernetwork. If a network device were to lose a device configuration file,another network device of the peer-to-peer communication network maydetect the loss and transmit a stored backup device configuration fileto the network device.

While only certain features of the disclosure have been illustrated anddescribed herein, many modifications and changes will occur to thoseskilled in the art. It is, therefore, to be understood that the appendedclaims are intended to cover all such modifications and changes as fallwithin the true spirit of the disclosure.

The invention claimed is:
 1. A system, comprising: a first networkdevice comprising a first processor and a first communication componentwherein the first network device is configured to perform an operationaccording to a device configuration file; and a second network devicecommunicatively coupled to the first network device via a peer-to-peer(P-P) communication network, wherein the second network device comprisesa second processor, a second communication component and a memorycomponent, wherein the second network device comprises a backup file ofthe device configuration file stored in the memory component, whereinthe second network device is configured to transmit the backup file ofthe device configuration file to the first network device using the P-Pcommunication network in response to detecting that the first networkdevice is lacking the device configuration file, wherein the P-Pcommunication network is configured to couple the first network deviceand the second network device via a sub-network, wherein the sub-networkis associated with a logical definition of one or more communicationchannels within the P-P communication network, and wherein the deviceconfiguration file defines a data endpoint associated with thesub-network.
 2. The system of claim 1, comprising an industrialautomation device coupled to the first network device, wherein theindustrial automation device comprises a motor starter, and wherein thefirst network device is configured to control, as part of the operation,an additional operation of the motor starter based on a setting of thedevice configuration file.
 3. The system of claim 1, wherein the firstnetwork device is configured to automatically transmit the backup fileof the device configuration file to the second network device inresponse to the first network device generating the device configurationfile.
 4. The system of claim 1, wherein the first network device isconfigured to automatically transmit the backup file of the deviceconfiguration file to a plurality of network devices via a smart wireconfiguration in response to the first network device generating thedevice configuration file.
 5. The system of claim 1, wherein the secondnetwork device is configured to detect that the first network device islacking the device configuration file based on data indicative of thefirst network device being added to the P-P communication network.
 6. Amethod, comprising: detecting, via a first network device comprising afirst processor, a first communication component, and a memorycomponent, that a second network device is lacking a deviceconfiguration file, wherein the second network device comprises a secondprocessor and a second communication component and wherein the firstnetwork device and the second network device couple to each otherthrough a peer-to-peer (P-P) communication network for an industrialautomation system; and transmitting, via the first network device, abackup configuration file stored in the memory component to the secondnetwork device using the P-P communication network in response todetecting that the second network device is lacking the deviceconfiguration file, wherein the backup configuration file corresponds tothe device configuration file, wherein the second network device isconfigured to perform an operation within the industrial automationsystem in response to a setting defined by the backup configurationfile, wherein the P-P communication network is configured to couple thefirst network device and the second network device via a sub-network,wherein the sub-network is associated with a logical definition of oneor more communication channels within the P-P communication network, andwherein the device configuration file defines a data endpoint associatedwith the sub-network.
 7. The method of claim 6, comprising receiving,via the first network device, the backup configuration file from thesecond network device after the second network device generates thedevice configuration file.
 8. The method of claim 6, comprisingselecting, via the first network device, a third network device from aplurality of network devices based on a physical proximity of the thirdnetwork device relative to the second network device, wherein thetransmitting of the backup configuration file uses the backupconfiguration file stored in the third network device.
 9. The method ofclaim 8, wherein transmitting the backup configuration file to thesecond network device comprises identifying the third network devicefrom the plurality of network devices based on a logical proximity ofthe third network device relative to the second network device.
 10. Themethod of claim 6, wherein transmitting the backup configuration file tothe second network device comprises identifying the first network devicefrom a plurality of network devices based on a time associated with thebackup configuration file stored in the first network device relative toa time associated with when each of a plurality of additional backupconfiguration files is stored on a respective network device.
 11. Themethod of claim 6, comprising receiving, via the first network device,the backup configuration file from the second network device via asub-network communicative coupling the first network device to thesecond network device.
 12. The method of claim 6, wherein detecting thatthe secondnetwork device is lacking the device configuration filecomprises: monitoring, via the first network device, a signal outputfrom the second network device; and detecting, via the first networkdevice, when the signal output changes.
 13. A tangible, non-transitorycomputer-readable medium configured to store instructions executable bya processor of an electronic device that, when executed by theprocessor, cause the electronic device to: discover a plurality of dataendpoints, wherein each data endpoint of the plurality of data endpointscorresponds to a respective network device coupled to a peer-to-peer(P-P) communication network; generate a device configuration file for afirst network device coupled to the P-P communication network based onrespective data endpoints of the plurality of data endpoints associatedwith the first network device, wherein the first network devicecomprises a first processor and a first communication component;transmit the device configuration file to the first network device usingthe P-P communication network, wherein the first network device isconfigured to perform an operation based on the device configurationfile; and transmit the device configuration file to a second networkdevice of the P-P communication network using the P-P communicationnetwork, wherein the second network device comprises a second processor,a second communication component, a memory component, wherein the memorycomponent is configured to store the device configuration file, whereinthe second network device is configured to transmit the deviceconfiguration file to the first network device as a backup configurationfile using the P-P communication network in response to detecting thatthe first network device is lacking the device configuration file,wherein the P-P communication network is configured to couple the firstnetwork device and the second network device via a sub-network, whereinthe sub-network is associated with a logical definition of one or morecommunication channels within the P-P communication network; and whereinthe device configuration file defines a data endpoint associated withthe sub-network.
 14. The non-transitory computer-readable medium ofclaim 13, comprising instructions that, when executed by the processor,cause the electronic device to discover the plurality of data endpointsat least in part by transmitting a plurality of test signal through theP-P communication network.
 15. The non-transitory computer-readablemedium of claim 13, comprising instructions that, when executed by theprocessor, cause the electronic device to transmit the deviceconfiguration file to a plurality of network devices comprising thesecond network device.
 16. The non-transitory computer-readable mediumof claim 15, comprising instructions that, when executed by theprocessor, cause the electronic device to identify the second networkdevice from the plurality of network devices based on a logicalproximity of the second network device relative to the first networkdevice, a physical proximity of the second network device relative tothe first network device, a time of when the backup configuration filewas generated, or any combination thereof.
 17. The non-transitorycomputer-readable medium of claim 13, wherein the instructions thatcause the electronic device to generate the device configuration filecomprise instructions that, when executed by the processor, cause theelectronic device to: determine a control operation to be performed bythe first network device; determine a type of device to receive datafrom the first network device; determine a third network device of theP-P communication network that corresponds to the type of device;associate the third network device and the first network device as adata endpoint pair that is configured to intercommunicate via asub-network coupling based on the device configuration file; and updatethe device configuration file to define the sub-network coupling forreference by the first network device after the first network device isconfigured with the device configuration file.